7.6. Content Deployment
In SharePoint 2010,
content deployment is a feature of the Web Content Management (WCM) that
allows multifarm topologies for deploying content from sites or site
collections to remote sites or site collections. You could use the
ability to transfer content in this way to create a staging environment
in which you have an authoring environment that needs to go to an
approval environment to be approved, and finally on to a production
environment. You can use this flexibility of content deployment in both
intranet environments and Internet-facing sites. Because you are
deploying the content between site collections, this feature can be used
between sites on the same server as well as sites on completely
different farms. Multiple farms can have a configuration in which you
have an Internet-facing Web site in one farm while another farm resides
behind a firewall. You make changes to the Web site in the farm behind
the firewall and then deploy those changes to the Internet-facing Web
site at specified intervals.
7.6.1. Configure Content Deployment
Before you can create
deployment paths and jobs, you must first enable the destination farm to
accept incoming jobs, as shown in Figure 58.
You can then specify which servers will be performing the import and
export operations in the farm to allow deployment jobs to be sent and
received by those servers in the farm. You can also enable encryption
for improved security during the deployment of data, and you can specify
the temporary storage location for files that are involved in the
deployment process.
Note:
Make sure you have plenty of
disk space on the temporary storage location folder, because some
deployment jobs can be quite large if the source site contains a large
amount of content in its lists and libraries.
7.6.2. Configure Content Deployment Paths and Jobs
In content deployment,
you are restricted to deploying the content in one direction—it is not a
two-way synchronization tool. To deploy content, you need to configure
both a path and job. The path defines the source site or site collection
as well as the destination site or site collection. The job defines the
frequency with which the content is deployed. Furthermore, you can
configure the deployment to affect only content that has changed since
the last deployment, so you are not deploying content that has not
changed. This reduces the amount of content being transferred.
Creating a Content Deployment Path
When a farm is enabled to accept incoming jobs, you can create the path
between the sites and also the jobs that utilize those paths. A path
in content deployment is a relationship between two specific site
collections that must be configured; you also must designate the
authentication method to use when a connection is established to
complete the deployment. To create a content deployment path, complete
the following steps using the Create Content Deployment Path page shown
in Figure 59.
Enter a path name and description.
Select the source Web application and the associate site or site collection.
Specify
the URL of the destination Central Administration website that will
receive the incoming content. Ensure that the website has been enabled
to receive incoming deployment jobs.
Specify the authentication method that should be used to establish the connection to the destination server.
Specify the destination Web application and the site or site collection that is receiving the content.
Indicate
whether to deploy user names and security information along with the
deployed content, such as the Access Control Lists (ACLs) and group
membership for the content stored in the document libraries.
Creating a Content Deployment Job
After you have defined a path, you can associate multiple jobs with the
path to utilize the relationship between site collections. The jobs you
create can be set up to deploy only certain sites in the site
collection as well as to identify when the job is scheduled to run. To
create a content deployment job, follow these steps using the Create
Content Deployment Job page shown in Figure 60.
Enter a job name and description.
Select a path to use for the job. (You can only associate the job with one path.)
Specify whether or not you want to create and use SQL Server snapshots for the job.
Choose whether you want to deploy the entire site collection or subsites contained in site collection.
Create a schedule for the job that defines how frequently the deployment should occur.
Choose if you want to deploy all the content or just changes since the last time the job ran.
Define the settings for the e-mail notification process for job successes and failures.
You can also configure reports that will follow the progress of the jobs as they transfer between the site collections.
7.6.3. Check Deployment of Specific Content
You use this option to
check the deployment status for a particular object. Type the URL of the
object in the URL box and then click Check Status to get details about
the source and destination of the deployment process.
8. Configuration Wizards
By default, the Configuration
Wizards functional category contains only one section, Farm
Configuration, and one option within that section, the Launch The Farm
Configuration Wizard link. Microsoft anticipates that additional wizards
will be added to SharePoint Central Administration, either by Microsoft
or other third-party vendors; when they are available, they can be
stored in this functional category.
8.1. Launch the Farm Configuration Wizard
If you chose not to run the Farm
Configuration Wizard during SharePoint installation, you can still run
it at a later time by accessing it here, through Central Administration.
You use this wizard to install and configure the numerous service applications available in SharePoint 2010.
After you launch the
wizard, you will be prompted to specify if you want the wizard to walk
you through the settings to install and configure the service
applications, which is the default, or if you prefer to configure
everything yourself. If you choose the option to configure the settings
yourself, you will exit out of the wizard.
If you choose the option Walk Me
Through The Wizard Settings, you will notice that any service
applications that have already been configured are unavailable. However,
if you have not installed any service applications before running
the wizard, all of the available service applications will be selected
to be installed and configured, except for the Lotus Notes Connector.
You can clear the check boxes
associated with any service applications that you don’t want the wizard
to install and configure, then simply run the wizard again at a later
date if you find that you require those services. After the wizard
completes, it may prompt you to create a site collection for your
intranet portal, and again you let the wizard create this site
collection or choose not to do so and create your own at your
convenience.
